Method and apparatus for changing network configuration in wireless communication system

ABSTRACT

The present disclosure relates to a communication method and system for converging a 5 th -Generation (5G) communication system for supporting higher data rates beyond a 4 th -Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. A method and an apparatus for network slicing are provided.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 17/172,498, filed on Feb. 10, 2021, which will be issued as U.S.Pat. No. 11,722,951 on Aug. 8, 2023, and is based on and claims priorityunder 35 U.S.C § 119(a) of a Korean patent application number10-2020-0019108, filed on Feb. 17, 2020, in the Korean IntellectualProperty Office, and of a Korean patent application number10-2020-0034684, filed on Mar. 20, 2020, in the Korean IntellectualProperty Office, the disclosure of each of which is incorporated byreference herein in its entirety.

BACKGROUND 1. Field

The disclosure relates to a method of changing the configuration of anetwork established in a wireless communication system. Moreparticularly, the disclosure relates to a method of slicing a network ina next-generation wireless communication system.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4^(th) generation (4G) communication systems, efforts havebeen made to develop an improved 5^(th) generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post long term evolution(LTE) System’.

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud radioaccess networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, coordinated multi-points (CoMP), reception-endinterference cancellation and the like.

In the 5G system, hybrid frequency shift keying (FSK) and quadratureamplitude modulation (QAM) (FQAM) and sliding window superpositioncoding (SWSC) as an advanced coding modulation (ACM), and filter bankmulti carrier (FBMC), non-orthogonal multiple access (NOMA), and sparsecode multiple access (SCMA) as an advanced access technology have beendeveloped.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofeverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing information technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies, suchas a sensor network, machine type communication (MTC), andmachine-to-machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud radioaccess network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

With the development of various information technology (IT)technologies, network equipment has evolved into a virtualized networkfunction (NF, hereinafter, may be used interchangeably with a ‘networkelement’) by applying virtualization technology, and virtualized NFs maybe implemented in a software form without physical limitations to beinstalled/operated in various types of clouds or data centers (DCs). Inparticular, the NF may be freely expanded, scaled, initiated, orterminated according to service requirements, a system capacity, or anetwork load. It should be noted that even if these NFs are implementedin a software form, the NFs do not exclude physical configurations,because the NFs should be basically driven on a physical configuration,for example, a fixed equipment. Further, NFs may be implemented onlywith a simple physical configuration, that is, hardware.

In order to support various services in these various networkstructures, network slicing technology has been introduced. Networkslicing is a technology that logically configures a network as a set ofnetwork functions (NF) for supporting a specific service and thatseparates the network from other slices. One terminal may access two ormore slices when receiving various services.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

Aspects of the disclosure are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the disclosure is to providea method and apparatus for effectively managing a network configuredwith network slices for supporting various services and preventingsignaling loads and collisions.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

In accordance with an aspect of the disclosure, a method performed by aservice communication proxy (SCP) entity in a wireless communicationsystem is provided. The method includes transmitting, to a networkrepository function (NRF) entity, a network function (NF) discoveryrequest message including first information associated with a target SCPentity, and receiving, from the NRF entity, an NF discovery responsemessage including second information associated with the target SCPentity based on the first information, wherein the first informationincludes a type of NF for the target SCP entity, the type of NF beingset to an SCP.

In the method, the first information includes at least one of NF setinformation associated with an NF entity served by the target SCP entityor a network slice related identifier associated with the target SCPentity.

In the method, the second information includes the type of NF for thetarget SCP entity, an NF identifier of the target SCP entity, and anaddress of the target SCP entity.

In the method, the second information includes at least one of a networkslice related identifier associated with the target SCP entity, SCPdomain information associated with another SCP entity interconnectedwith the SCP entity, NF set information associated with an NF entityserved by the SCP entity, or endpoint addresses accessible via thetarget SCP entity.

In accordance with another aspect of the disclosure, a servicecommunication proxy (SCP) entity in a wireless communication system isprovided. The SCP entity includes a transceiver, and at least oneprocessor coupled with the transceiver and configured to transmit, to anetwork repository function (NRF) entity, a network function (NF)discovery request message including first information associated with atarget SCP entity, and receive, from the NRF entity, an NF discoveryresponse message including second information associated with the targetSCP entity based on the first information, wherein the first informationincludes a type of NF for the target SCP entity, the type of NF beingset to an SCP.

In accordance with another aspect of the disclosure, a method performedby a network repository function (NRF) entity in a wirelesscommunication system is provided. The method includes receiving, from aservice communication proxy (SCP) entity, a network function (NF)discovery request message including first information associated with atarget SCP entity, and transmitting, to the SCP entity, an NF discoveryresponse message including second information associated with the targetSCP entity based on the first information, wherein the first informationincludes a type of NF for the target SCP entity, the type of NF beingset to an SCP.

In accordance with another aspect of the disclosure, a networkrepository function (NRF) entity in a wireless communication system isprovided. The NRF entity includes a transceiver, and at least oneprocessor coupled with the transceiver and configured to receive, from aservice communication proxy (SCP) entity, a network function (NF)discovery request message including first information associated with atarget SCP entity, and transmit, to the SCP entity, an NF discoveryresponse message including second information associated with the targetSCP entity based on the first information, wherein the first informationincludes a type of NF for the target SCP entity, the type of NF beingset to an SCP.

According to disclosed embodiments of the disclosure, it is possible toefficiently use radio resources and efficiently provide various servicesto users by managing network slices in units of sets.

In addition, according to an embodiment of the disclosure, the user canefficiently access a desired network function entity by efficientlysearching for a plurality of network function entities providing variousservices.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a diagram illustrating a wireless communication systemaccording to an embodiment of the disclosure;

FIG. 2 is a diagram illustrating a method for selecting a network slicewhen a new base station (RAN) is added or configuration information of abase station is changed in a mobile communication system according to anembodiment of the disclosure;

FIG. 3 is a diagram illustrating a method for more effectively managingnetwork slice selection assistance information (NSSAI) availabilityaccording to an embodiment of the disclosure;

FIG. 4A is a diagram illustrating an overall method for managing sliceinformation in units of sets according to an embodiment of thedisclosure;

FIG. 4B is a diagram illustrating a method for a master access andmobility management function (AMF) to manage slice information in unitsof sets according to an embodiment of the disclosure;

FIG. 5 is a diagram illustrating a method for managing a profile inunits of network function (NF) sets according to an embodiment of thedisclosure;

FIG. 6 is a diagram illustrating a method for creating or adding an NFset, or updating configuration information of the NF set according to anembodiment of the disclosure;

FIG. 7 is a diagram illustrating an AMF selection process using a masterAMF according to an embodiment of the disclosure;

FIG. 8 is a diagram illustrating an NF registration process according toan embodiment of the disclosure;

FIG. 9 is a diagram illustrating an NF registration process according toan embodiment of the disclosure;

FIG. 10 is a diagram illustrating an NF registration process accordingto an embodiment of the disclosure;

FIG. 11 is a diagram illustrating an NF registration process accordingto an embodiment of the disclosure;

FIG. 12 is a diagram illustrating a method for an NF to receive servicecommunication proxy (SCP) information through an NRF according to anembodiment of the disclosure;

FIG. 13 is a diagram illustrating a terminal equipment according to anembodiment of the disclosure;

FIG. 14 is a diagram illustrating a base station equipment according toan embodiment of the disclosure; and

FIG. 15 is a diagram illustrating an NF entity according to anembodiment of the disclosure.

The same reference numerals are used to represent the same elementsthroughout the drawings.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of thedisclosure is provided for illustration purpose only and not for thepurpose of limiting the disclosure as defined by the appended claims andtheir equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Terms used in the disclosure are used only to describe a specificembodiment of the disclosure, and may be not intended to limit the scopeof other embodiments. Terms including technical and scientific termsused herein have the same meaning as commonly understood by one ofordinary skill in the art to which this disclosure belongs. Among theterms used in the disclosure, those defined in commonly useddictionaries may be interpreted as having a meaning that is identical orsimilar to their meaning in the context of the specification andrelevant art and should not be interpreted in an idealized or overlyformal sense unless expressly so defined herein. In some cases, eventerms defined in the disclosure should not be interpreted to excludeembodiments of the disclosure.

In various embodiments of the disclosure described below, a hardwareapproach is described as an example. However, as various embodiments ofthe disclosure include technologies using both hardware and software,various embodiments of the disclosure do not exclude a software-basedapproach.

Here, the same or similar reference symbols are used throughout thedrawings to refer to the same or like parts. Descriptions of functionsand structures well known in the art may be omitted to avoid obscuringthe subject matter of the disclosure.

In the following description of embodiments of the disclosure,descriptions of technical details well known in the art and not directlyrelated to the disclosure may be omitted. This is to more clearly conveythe gist of the disclosure without obscurities by omitting unnecessarydescriptions.

Likewise, in the drawings, some elements are exaggerated, omitted, oronly outlined in brief. In addition, the size of each element does notnecessarily reflect the actual size. The same reference symbols are usedthroughout the drawings to refer to the same or corresponding parts.

Advantages and features of the disclosure and methods for achieving themwill be apparent from the following detailed description of embodimentstaken in conjunction with the accompanying drawings. However, thedisclosure is not limited to the embodiments disclosed below but may beimplemented in various different ways, the embodiments are provided onlyto complete the disclosure and to fully inform the scope of thedisclosure to those skilled in the art to which the disclosure pertains,and the disclosure is defined only by the scope of the claims. The samereference symbols are used throughout the specification to refer to thesame parts.

Meanwhile, it will be appreciated that blocks of a flowchart and acombination of flowcharts may be executed by computer programinstructions. These computer program instructions may be loaded on aprocessor of a general purpose computer, special purpose computer, orprogrammable data processing equipment, and the instructions executed bythe processor of a computer or programmable data processing equipmentcreate a means for carrying out functions described in blocks of theflowchart. To implement the functionality in a certain way, the computerprogram instructions may also be stored in a computer usable or readablememory that is applicable in a specialized computer or a programmabledata processing equipment, and it is possible for the computer programinstructions stored in a computer usable or readable memory to producearticles of manufacture that contain a means for carrying out functionsdescribed in blocks of the flowchart. As the computer programinstructions may be loaded on a computer or a programmable dataprocessing equipment, when the computer program instructions areexecuted as processes having a series of operations on a computer or aprogrammable data processing equipment, they may provide operations forexecuting functions described in blocks of the flowchart.

Additionally, each block of a flowchart may correspond to a module, asegment or a code containing one or more executable instructions forexecuting one or more logical functions, or to a part thereof. It shouldalso be noted that functions described by blocks may be executed in anorder different from the listed order in some alternative cases. Forexample, two blocks listed in sequence may be executed substantially atthe same time or executed in reverse order according to thecorresponding functionality.

Here, the word “unit”, “module”, or the like used in the embodiments mayrefer to a software component or a hardware component, such as a fieldprogrammable gate array (FPGA) or application-specific integratedcircuit (ASIC) capable of carrying out a function or an operation.However, “unit” or the like is not limited to hardware or software. Aunit or the like may be configured so as to reside in an addressablestorage medium or to drive one or more processors. For example, units orthe like may refer to components, such as a software component,object-oriented software component, class component or task component,processes, functions, attributes, procedures, subroutines, program codesegments, drivers, firmware, microcode, circuits, data, databases, datastructures, tables, arrays, or variables. A function provided by acomponent and unit may be a combination of smaller components and units,and it may be combined with others to compose larger components andunits. Components and units may be implemented to drive one or moreprocessors in a device or a secure multimedia card.

Hereinafter, the disclosure relates to a method and apparatus forsupporting various services in a wireless communication system.Specifically, the disclosure describes a technology for providingvarious services by supporting mobility of a terminal in a wirelesscommunication system.

Those terms used in the following description for identifying an accessnode, indicating a network entity or network function (NF), indicatingmessages, indicating an interface between network entities, andindicating various identification information are taken as illustrationfor ease of description. Accordingly, the disclosure is not limited bythe terms to be described later, and other terms referring to objectshaving an equivalent technical meaning may be used.

For convenience of description below, the disclosure may use terms andnames defined in the 3^(rd) generation partnership project (3GPP) longterm evolution (LTE) and 5^(th) generation (5G) standards. However, thedisclosure is not limited by the above terms and names, and may beequally applied to systems conforming to other standards.

In the disclosure, entities that exchange information for access controland state management will be collectively described as an NF. Forexample, the NF may be at least one entity among an access and mobilitymanagement function (AMF) entity, a session management function (SMF)entity, and a network slice selection function (NSSF) entity. However,embodiments of the disclosure may be equally applied even when an NF isactually implemented as an instance (e.g., AMF instance, SMF instance,or NSSF instance).

In the disclosure, an instance may indicate a state where a specific NFexists in the form of software code and can be executed on a physicalcomputing system, for example, a specific computing system existing onthe core network to perform the function of the NF by using physicalor/and logical resources allocated from the computing system. Hence,this may mean that an instance of each NF, such as an AMF instance andan SMF instance may use physical or/and logical resources allocated froma specific computing system existing on the core network for thecorresponding NF operation. Consequently, an NF instance, which usesphysical or/and logical resources allocated from a specific computingsystem existing on the network for the NF operation, may perform thesame operation as a case where an NF entity, such as a physical AMF orSMF exists.

FIG. 1 illustrates a wireless communication system according to anembodiment of the disclosure.

Referring to FIG. 1 , as a node using a radio channel in the wirelesscommunication system, a base station (radio access node (RAN)) 110 and aterminal (user equipment (UE)) 120 are illustrated. Although only onebase station 110 and one terminal 120 are shown in FIG. 1 , another basestation identical or similar to the base station 110 may be furtherincluded. Additionally, in FIG. 1 , only a case where only one terminal120 performs communication within one base station 110 is illustrated.However, it is evident that a plurality of terminals can actuallycommunicate within one base station 110.

The base station 110 is a network infrastructure that provides radioaccess to the terminal 120. The base station 110 has a coverage definedas a certain geographic area based on the distance at which a signal canbe transmitted (not shown in FIG. 1 ). Besides radio access node (RAN),the base station 110 may be referred to as access point (AP), eNodeB(eNB), 5G node, wireless point, transmission/reception point (TRP), oras another term having an equivalent technical meaning.

The terminal 120 is a device used by a user and performs communicationwith the base station 110 through a radio channel. In some cases, theterminal 120 may be operated without user involvement. For example, theterminal 120 may be a device that performs machine type communication(MTC), and may be not carried by a user. The terminal 120 illustrated inFIG. 1 may include at least one user portable device, and may include atleast one MTC device. The terminal 120 in FIG. 1 may be referred to asuser equipment (UE), mobile station, subscriber station, remoteterminal, wireless terminal, user entity, or as another term having anequivalent technical meaning.

The AMF entity 131 may be a network entity that manages wireless networkaccess and mobility for the terminal 120. The SMF entity 132 may be anetwork entity that manages a connection to a packet data network forproviding packet data to the terminal 120. The connection between theterminal 120 and the SMF 132 may be a PDU session.

The user plane function (UPF) entity 133 may be a gateway that deliverspackets transmitted and to be received by the terminal 120 or a networkentity serving as a gateway. The UPF 133 may be connected to the datanetwork (DN) 140 connected to the Internet, and may provide a path fortransmitting and receiving data between the terminal 120 and the DN 140.Hence, the UPF 133 may route data to be delivered to the Internet amongpackets transmitted by the terminal 120 to an Internet data network.

The network slice selection function (NSSF) entity 134 may be a networkentity that performs a network selection operation described in thedisclosure, for example, an operation for selecting a network slice. Theoperation of the NSSF entity 134 will be described below with referenceto the following drawings.

The authentication server function (AUSF) entity 151 may be an equipment(network entity) that provides a service for processing subscriberauthentication.

The network exposure function (NEF) entity 152 may be a network entitythat can access management information of the terminal 120 on a 5Gnetwork, subscribe a mobility management event for the terminal,subscribe a session management event for the terminal, make a requestfor session-related information, set charging information for theterminal, make a change request for the PDU session policy of theterminal, and transmit small data about the terminal.

The network repository function (NRF) entity 153 may be an NF (networkentity) that can store state information of NFs and process a requestfor finding an NF to which other NFs can make access.

The policy and charging function (PCF) entity 154 may be a networkentity that applies a service policy, a charging policy, and a PDUsession policy of the mobile network operator to the terminal 120.

The unified data management (UDM) entity 155 may be a network entitythat stores information about the subscriber or/and the terminal 120.

The application function (AF) entity 156 may be an NF (network entity)that provides services to users in cooperation with a mobilecommunication network.

The service communication proxy (SCP) entity 157 is an NF (networkentity) that provides functions, such as NF discovery for communicationbetween NFs and message transfer between NFs. The SCP 157 can operate inan integrated form with the NRF 153 according to the operator'sselection. In this case, the SCP 157 may include the function of the NRF153, or, conversely, the NRF 153 may include the function of the SCP157.

Hereinafter, for ease of description, entities that exchange informationfor access control and state management will be collectively describedas an NF. For example, the NF may be one of NF entities, such as theaccess and mobility management function (AMF) entity, the sessionmanagement function (SMF) entity, and the network slice selectionfunction (NSSF) entity. However, embodiments of the disclosure may beequally applied even when an NF is actually implemented as an instance(AMF instance, SMF instance, or NSSF instance).

FIG. 2 is a diagram illustrating a method that, when a new base station(RAN) is added in a mobile communication system or configurationinformation of a base station (e.g., tracking area (TA) supported by thebase station, NW slice (logical network identified by single networkslice selection assistance information (S-NSSAI)) is added or updated,can notify this to other NFs and enables a network slice suitable forthe subscriber service to be selected accordingly according to anembodiment of the disclosure.

Referring to FIG. 2 , a base station may be newly added or may start tooperate, or the configuration of the base station, that is, the trackingarea (TA) or a NW slice (logical network identified by S-NSSAI)supported by the base station may be added or updated at operation 201.

The base station may perform an NG setup procedure if a new relationshipand connection for network configuration and management with the AMF isrequired, or may perform a RAN configuration update procedure if thereis an existing connection at operation 202. Here, the request messagesent by the base station may include the name and identifier of the basestation and a list of TAs supported by the base station, and the TA listmay include, for each TA, one or more S-NSSAIs supported in the TA.

The AMF may determine whether to consider addition or update of networkslice and TA information in the slice selection process according to theinformation received from the base station. If the network configurationfor slice selection is updated, the AMF may invoke the NSSF (which canbe replaced with another NF like the NRF or SCP that manages and findsnetwork state information) for a service of NSSAI availability update atoperation 203. The network slice selection assistance information(NSSAI) may be composed of one or more S-NSSAIs. Similarly, the servicerequest message may include a list of TAIs and NSSAIs to be added orupdated.

The NSSF may update or add information about a slice and an area (TA)where the slice is supported if necessary to update it according to therequest from the AMF at operation 204. Here, the data stored by the NSSFmay be identified by using the identity (ID) of the AMF instance havingmade the request. The NSSF may determine the time of application for theupdated NSSAI availability.

The NSSF transmits a response for the request from the AMF, in whichcase when the slice information (AuthorizedNssaiAvailability) allowed tobe used by the AMF is updated or added, this may also be notified atoperation 205. Here, to match the application time of the updatedavailability with other AMFs, the NSSF may transmit the correspondingtime information as a portion of the response to the AMF. Upon receivingthe time information, the AMF operates with application of the updatedinformation from the time point when the corresponding time condition issatisfied.

The AMF transmits a response for the request from the base station, inwhich case configuration information of the AMF may be included in theresponse at operation 206. If the network configuration supported by theAMF (TA, supported NSSA, PLMN, or the like) is updated at operation 205,the base station is notified through this process.

The disclosure proposes a method that can more effectively managenetwork slices and prevent signaling loads and collisions in a networkconfiguration composed of NF sets.

In the embodiment of FIG. 2 , if two or more AMFs (including instances)are included in one AMF set and that set supports the same TAs andslices, addition or configuration update of a base station must bedelivered to all NFs (e.g., AMF) belonging to the set and all NFsreceiving this may have to transmit a request to other NSSFs (or NRFs)to notify the addition/update of their NSSAI availability. In this case,if the number of base stations is large or the number of AMFs in the setis large, a signaling overload may occur, or a mismatch or collision mayoccur in the network configuration information due to a time differencein transmission and processing of signaling.

FIG. 3 illustrates a method for more effectively managing NSSAIavailability according to an embodiment of the disclosure.

In this embodiment of the disclosure, NSSAI availability management maybe performed by the master AMF (or, default AMF) belonging to the AMFset.

One of the AMFs belonging to the AMF set may be selected as the masterAMF. A designated AMF may be set to play the master role, or AMFs may beselected alternately in a round robin fashion to play the master role.Here, information may be exchanged between the AMFs to notify that onlyone AMF operates as the master in the AMF set at a specific time.

Referring to FIG. 3 , a base station may be newly added or may start tooperate, or the configuration of the base station, that is, the trackingarea (TA) or a NW slice (logical network identified by S-NSSAI)supported by the base station may be added or updated at operation 301.

The base station may perform an NG setup procedure if a new relationshipand connection for network configuration and management with theconnected AMF and master AMF is required, or may perform a RANconfiguration update procedure if there is an existing connection atoperations 302, 303. Here, the request message sent by the base stationmay include the name and identifier of the base station and a list ofTAs supported by the base station, and the TA list may include, for eachTA, one or more S-NSSAIs supported in the TA.

The master AMF may determine whether to consider addition or update ofnetwork slice and TA information in the slice selection processaccording to the information received from the base station. If thenetwork configuration for slice selection is updated, the master AMF mayinvoke the NSSF (which can be replaced with another NF like the NRF orSCP that manages and finds network state information) for a service ofNSSAI availability update at operation 304. The network slice selectionassistance information (NSSAI) may be composed of one or more S-NSSAIs.Similarly, the service request message may include a list of TAIs andNSSAIs to be added or updated.

The NSSF may update or add information about a slice and an area (TA)where the slice is supported if necessary to update it according to therequest from the master AMF at operation 305. Here, the data stored bythe NSSF may be identified by using the identity (ID) of the master AMFinstance having made the request. The NSSF may determine the time ofapplication for the updated NSSAI availability.

The NSSF transmits a response for the request from the master AMF, inwhich case when the slice information (e.g.,AuthorizedNssaiAvailability) allowed to be used by the AMF is updated oradded, this may also be notified to the master AMF at operation 306.Here, to match the application time of the updated availability withother AMFs, the NSSF may transmit the corresponding time information asa portion of the response to the master AMF. Upon receiving the timeinformation, the master AMF operates with application of the updatedinformation from the time point when the corresponding time condition issatisfied.

The NSSF may also update the NSSAI available information of other AMFinstances belonging to the AMF set requested from the master AMF atoperation 307. For example, the NSSF may find an AMF set related to theslice information received from the master AMF, find AMF instancesbelonging to the set, and update the NSSAI available informationidentified by the instance IDs of the AMF instances together.

If the NSSAI availability information is updated for other AMF instancesbelonging to the AMF set and AuthorizedNssaiAvailability is updated oradded for each AMF instance, the NSSF may transmit a message notifyingthis to each AMF instance at operation 308. This can be performed byusing the NSSAI availability update notification service. Here, to matchthe application time of the updated availability with other AMFinstances, the NSSF may transmit the corresponding time information as aportion of the message to the AMF. Upon receiving the time information,the AMF operates with application of the updated information from thetime point when the corresponding time condition is satisfied.

The AMFs transmit a response for the request message from the basestation, in which case configuration information of the AMF may beincluded in the response at operation 309. If the network configurationsupported by the AMF (TA, supported NSSA, PLMN, or the like) is updatedin the NSSF, the AMF may notify this to the base station through theresponse message.

In addition, to address the above issue, the disclosure proposes amethod that defines information shared commonly in a specific NF setseparately as an NF set profile and uses this to improve signalingefficiency and match state information.

The NF set profile is stored or managed by using an identifier that canidentify the corresponding NF set (NF set ID or ID of the NF instancethat manages NF set information). The information shown in Table 1 maybe included in the NF set profile, and any type of information shared byNF instances in the NF set (e.g., serving scope: supported area, or thelike) may be added.

TABLE 1 Attribute name P Cardinality Description nfSetId M 1 ID that canrefer to common profile of Nf set. ID of instance that manages Nf setprofile may also be used nfType M 1 Type of NF belonging to NF set(e.g., AMF, SMF, or the like) nfStatus M 1 Status of NF set (idle,active, or the like) nfSetName O 0 . . . 1 Human-readable name of NF setplmnList C 0 . . . N List of PLMN IDs commonly supported by NF setsnpnList C 0 . . . N SNPN(s) supported by NF set sNssais O 0 . . . NS-NSSAIs supported by NF set perPlmnSnssaiList O 0 . . . N S-NSSAIssupported by NF set for each PLMN . . .

Likewise, information on available slices (NSSAI availability) can beshared and managed per set. In this case, the unit for storing/managingthe slice information in the NF is not the ID of each AMF but the AMFset ID or the ID of the NF that manages information for each set. Forexample, the resource for which the NSSF stores correspondinginformation is managed per set, and may be identified by an AMF set IDor an ID of the NF that manages information for each set.

NSSAI availability information per set (NSSAI availability per set) maybe composed of the following data shown in Table 2.

TABLE 2 Attribute name Data type P Cardinality DescriptionsupportedNssaiAvailabilityData array M 1 . . . N This IE shall containthe information (SupportedNssaiAvailabilityData) regarding the S-NSSAIs,the NF set (e.g., AMF set) and the 5G-AN supports TA. supportedFeaturesSupportedFeatures C 0 . . . 1 This IE shall be present if at least oneoptional feature defined in clause 6.2.8 is supported. nfInstanceIdNfInstanceId 0 0 . . . N This IE may be included to indicate the NF(e.g., AMF) instances identifier serving the TAIs where the NSSAI isavailable. amfSetId string O 0 . . . 1 This IE may be included toindicate the AMF set identifier for the AMFs serving the TAIs where theNSSAI available. When present, this IE shall be constructed from PLMN-ID(i.e., three decimal digits MCC and two or three decimal digits MNC),AMF Region Id (8 bit), and AMF Set Id (10bit). Pattern: ‘{circumflexover ( )}[0-9]{3}-[0-9]{2-3}-[A-Fa-f0- 9]{2}-[0-3][A-Fa-f0-9]{2}$’

supportedNssaiAvailabilityData may be configured as shown in Table 3below.

TABLE 3 Attribute name Data type P Cardinality Description tai Tai M 1 .. . N This IE shall contain the identifier of the Tracking Area.supportedSnssaiList array(Snssai) C 0 . . . 1 This IE shall contain theS-NSSAI(s) supported by the AMF for the TA.

FIGS. 4A and 4B are diagrams illustrating a method for managing sliceinformation in units of sets according to various embodiments of thedisclosure.

FIG. 4A is a diagram illustrating an overall process of managing sliceinformation in units of sets according to the disclosure.

Referring to FIG. 4A, a base station may be newly added or may start tooperate, or the configuration of the base station, that is, the trackingarea (TA) or a NW slice (logical network identified by S-NSSAI)supported by the base station may be added or updated at operation 401.

The base station may perform an NG setup procedure if a new relationshipand connection for network configuration and management with theconnected AMF and master AMF is required, or may perform a RANconfiguration update procedure if there is an existing connection atoperations 402, 403. Here, the request message sent by the base stationmay include the name and identifier of the base station and a list ofTAs supported by the base station, and the TA list may include, for eachTA, one or more S-NSSAIs supported in the TA.

The master AMF may determine whether to consider addition or update ofnetwork slice and TA information for the AMF set in the slice selectionprocess according to the information received from the base station. Ifthe network configuration for slice selection is updated, the master AMFmay invoke the NSSF (which can be replaced with another NF like the NRFor SCP that manages and finds network state information) for a serviceof NSSAI availability update in units of sets at operation 404. Theservice request may include the NSSAI availability information per setdescribed above.

The NSSF may update or add information about a slice to be applied tothe set and an area (TA) where the slice is supported if necessary toupdate it according to the request from the master AMF at operation 405.Here, the data stored by the NSSF may be identified by using theidentity (ID) of the AMF set having made the request. The NSSF maydetermine the time of application for the updated NSSAI availability perset.

The NSSF transmits a response for the request from the master AMF, inwhich case when the slice information (e.g.,AuthorizedNssaiAvailability) allowed to be used by the AMF set isupdated or added, this may also be notified at operation 406. Here, tomatch the application time of the availability updated at operation 405with other AMFs, the NSSF may transmit the corresponding timeinformation as a portion of the response to the master AMF. Uponreceiving the time information, the master AMF operates with applicationof the updated information from the time point when the correspondingtime condition is satisfied.

The NSSF may also update the NSSAI available information of other AMFinstances belonging to the AMF set requested from the master AMF atoperation 407. For example, the NSSF may find an AMF set for the sliceinformation received from the master AMF, find AMF instances belongingto the set, and update the NSSAI available information identified by theinstance IDs of the AMF instances together.

The NSSF may notify the NSSAI availability information per set to otherAMF instances belonging to the AMF set at operation 408. For example,when AuthorizedNssaiAvailability per set is updated or added, the NSSFmay transmit a message for notifying this to each AMF instance. This canbe performed by using the NSSAI availability update notificationservice. Here, to match the application time of the updated availabilitywith other AMF instances, the NSSF may transmit the corresponding timeinformation as a portion of the message to the AMF. Upon receiving thetime information, the AMF operates with application of the updatedinformation from the time point when the corresponding time condition issatisfied.

Each AMF instance may separately update its own NSSAI availableinformation by using the authorized slice information per set receivedfrom the NSSF at operation 409.

The AMFs including the master AMF transmit a response for the requestmessage from the base station, in which case configuration informationof the AMF may be included in the response at operation 410. If thenetwork configuration supported by the AMF (TA, supported NSSA, PLMN, orthe like) is updated in the NSSF, the AMF may notify this to the basestation through the response message.

FIG. 4B is a diagram illustrating operations of the master AMF accordingto a time series flow in relation to the embodiment described in FIG. 4Aaccording to an embodiment of the disclosure.

Referring to FIG. 4B, when a new relationship and connection isgenerated for the configuration and management of the AMF, the masterAMF may receive a RAN configuration information update request messagefrom the base station for requesting an NG setup procedure or RANconfiguration update at operation 421.

The master AMF may determine whether a network configuration update,such as adding or changing network slice and TA information, hasoccurred for the AMF set based on the RAN configuration updateinformation message received from the base station at operation 422.

If the network configuration for slice selection is updated, the masterAMF may transmit the NSSF (which can be replaced with another NF likethe NRF or SCP that manages and finds network state information) anupdate request message for NSSAI availability update in units of sets toreceive a slice service under the network configuration updated byreflecting the above network configuration update at operation 423.

Thereafter, the NSSF updates or adds network configuration updateinformation by using the AMF set identifier included in the per-setupdate request message from the master AMF and transmits a response forthe update request to the master AMF, and the master AMF may receive itat operation 424.

The master AMF may transmit a response including AMF configurationinformation to the base station according to the slice informationupdated in units of sets at operation 425. Update information of thenetwork configuration (TA, supported NSSAI, PLMN, or the like) supportedby the AMF may be transmitted to the base station through this.

FIG. 5 is a diagram illustrating a method for managing a profile inunits of NF sets according to an embodiment of the disclosure.

In this embodiment of the disclosure, the management of the NF setprofile may be performed by the master NF (or, default AMF) belonging tothe NF set. One of the NFs belonging to the NF set may be selected asthe master NF, where a designated NF instance may be set to play themaster role, or NF instances may be selected alternately in a roundrobin fashion to play the master role. Here, information may beexchanged between the NF instances to notify that only one NF instanceoperates as the master in the NF set at a specific time.

Referring to FIG. 5 , an NF set may be newly created or added, orconfiguration information of an NF set may be updated at operation 501.Here, the configuration information of an NF set may include a set ofparameters or attributes that are shared by all NF instances belongingto the NF set and applied in common.

The master NF may perform a process for registering the profile of theNF set to which it belongs with the NRF (or SCP) at operation 502. Here,an NF register or NF set register service can be invoked, and theservice request may include the identifier (ID) of the NF set to beregistered and NF set profile. The NF set profile may includeidentifiers of NF instances belonging to the NF set.

The NRF may use the received information to store the profile of the NFset and generate resources for this at operation 503. Thereafter, theresource for the NF set profile can be identified by the NF set ID.

The NRF transmits a response for the request to the master NF atoperation 504.

The NRF may deliver the NF set profile to other NF instances belongingto the NF set to notify the created/updated set profile at operation505. Here, the NRF may use an NF status notify or NF set status notifyservice.

Those NF instances having received a notification from the NRF maytransmit an acknowledgment for the notification to the NRF at operation506.

FIG. 6 is a diagram illustrating a method for creating or adding an NFset, or updating configuration information of the NF set according to anembodiment of the disclosure.

Referring to FIG. 6 , an NF set may be newly created or added, orconfiguration information of an NF set may be updated at operation 601.Here, the configuration information of an NF set may include a set ofparameters or attributes that are shared by all NF instances belongingto the NF set and applied in common.

The master NF may perform a process for registering the profile of theNF set to which it belongs with the NRF (or, SCP) at operation 602.Here, an NF register or NF set register service can be invoked, and theservice request may include the identifier (ID) of the NF set to beregistered and NF set profile. The NF set profile may includeidentifiers of NF instances belonging to the NF set.

The NRF may use the received information to store the profile of the NFset and generate resources for this at operation 603. Thereafter, theresource for the NF set profile can be identified by the NF set ID.

The NRF transmits a response for the request to the master NF atoperation 604.

If the registration of the NF set profile is successful, the master NFmay transmit the NF set profile to other NF instances to notify thecreated/updated set profile at operation 605. Here, the master NF mayuse an NF status notify or NF set status notify service or a heartbeatservice.

Those NF instances having received a notification from the master NFtransmit an acknowledgment for the notification to the master NF atoperation 606.

FIG. 7 is a diagram illustrating an AMF selection process using a masterAMF. The role and selection scheme of the master AMF are the same asthose disclosed in FIGS. 3, 4A, and 4B according to an embodiment of thedisclosure.

Referring to FIG. 7 , the terminal may transmit an RRC messagecontaining a NAS message for registration to the base station atoperation 701. Here, the terminal may include slice information (NSSAI)to be accessed by it as an AS layer parameter.

The base station may determine whether it is possible to perform AMFselection by using the identifier (ID) used by the terminal, sliceinformation, and configured information. If the base station cannotperform AMF selection using the slice information or AS layer sliceinformation is not included in the message received from the terminal atoperation 702, the base station selects the master (or default) AMF andforwards the initial UE message received from the terminal to the masterAMF at operation 703.

The master AMF may receive subscription information from the UDM ifnecessary, in which case slice information and subscribed S-NSSAIsapplicable to the subscriber may be received at operation 704. If theterminal includes selected slice information (requested NSSAI) in theNAS layer, the master AMF may take this into account and selects an AMFbased on the subscription information received from the UDM at operation705. If the master AMF can provide a service to the terminal, itperforms the remaining portion of the registration process. If anotherAMF is selected, the master AMF transmits the base station a reroute NASmessage including information for identifying the selected AMF (AMFinformation, AMF set information, or other master AMF information) andan initial UE message (registration request) received from the terminalat operation 706.

The base station may select again an AMF to which the request of theterminal is to be transmitted by using the information received from themaster AMF at operation 707. If an AMF is designated and interworkingwith the designated AMF is possible, the base station may select thedesignated AMF. If AMF set information is received, one AMF can beselected from the corresponding AMF set. If another master AMFinformation is received, the base station may select the correspondingmaster AMF and transmit a message thereto.

FIG. 8 is a diagram illustrating an NF registration process according toan embodiment of the disclosure.

Referring to FIG. 8 , an NF of the network may transmit an NFregistration request message to the NRF to perform an NF registerprocess for registering its information at operation 801. Here, therequest message transmitted by the NF may include the profile of the NF,and may also include information about supported features indicatingfunctions supported by the NF. In particular, indications of whetherindirect communication, delegated discovery, SM context transfer,binding indication, and NF set are supported as enhancements to the SBA,among the functions supported by the NF, may be included. Informationabout the supported features may be included as a portion of the NFprofile, or may be separated from the NF profile and included in therequest message as separate data.

The NRF transmits a response message for the request of the NF atoperation 802, in which case the response message may include supportedfeatures available in the network where the NF is currently registered.The contents and message composition that may be included in thesupported features may be the same as those of the supported featuresincluded in the request message. In addition, the response of the NRFmay additionally include information to be applied when the NF uses theSCP in the network. The SCP information may include the address of theSCP, the operation mode of the SCP (one of modes A, B, C and D), whetherindirect communication is used, and whether delegated discovery is used.

The NF stores the information received from the NRF, and performssubsequent operations by using the received information (whether theSCP, indirect communication, or delegated discovery is used) atoperation 803.

FIG. 9 is a diagram illustrating an NF registration process according toan embodiment of the disclosure.

With reference to FIG. 9 , an NF of the network may transmit an NFregistration request message to the NRF to perform an NF registerprocess for registering its information at operation 901. Here, therequest message transmitted by the NF may include the profile of the NF,and may also include information about supported features indicatingfunctions supported by the NF. In particular, indications of whetherindirect communication, delegated discovery, SM context transfer,binding indication, and NF set are supported as enhancements to the SBA,among the functions supported by the NF, may be included. Informationabout the supported features may be included as a portion of the NFprofile, or may be separated from the NF profile and included in therequest message as separate data. In this case, the SCP can play a roleof receiving and forwarding messages between the NF and the NRF. Forexample, the SCP may receive a registration request message from the NFand forward it to the NRF.

The NRF transmits a response for the request of the NF at operation 902,in which case the response message may include supported featuresavailable in the network where the NF is currently registered. Thecontents and message composition that may be included in the supportedfeatures may be the same as those of the supported features included inthe request message.

The response message transmitted by the NRF is first received by theSCP, and the SCP may include SCP operation information in the responsemessage before forwarding at operation 903. The SCP information mayinclude the address of the SCP, the operation mode of the SCP (one ofmodes A, B, C and D), whether indirect communication is used, andwhether delegated discovery is used. The SCP may transmit the NF aresponse message including the above information in addition to theinformation received from the NRF.

The NF stores the information received from the NRF (and the SCP), andmay perform subsequent operations by using the received information(whether the SCP, indirect communication, or delegated discovery isused) at operation 904.

FIG. 10 is a diagram illustrating an NF registration process accordingto an embodiment of the disclosure.

Referring to FIG. 10 , one NF of the network may transmit a discoveryrequest message to the NRF to find or select another NF or receiveinformation thereof at operation 1001. Here, the request messagetransmitted by the NF may include information related to the target tobe found. To discover a desired NF, the NF may include indications ofwhether indirect communication, delegated discovery, SM contexttransfer, binding indication, and NF set are supported as enhancementsto the SBA in the request message as query parameters.

The NRF searches for a candidate NF that satisfies the condition for therequest of the NF and transmits a response at operation 1002. Theresponse message may include information about candidate NFs that therequesting NF can select and supported features of the candidate NFs.The response of the NRF may additionally include information to beapplied when the requesting NF uses the SCP in the network tocommunicate with the candidate NFs. The SCP information may include theaddress of the SCP, the operation mode of the SCP (one of modes A, B, Cand D), whether indirect communication is used, and whether delegateddiscovery is used.

The NF stores the information received from the NRF, and may performsubsequent operations by using the received information (informationabout candidate NFs, whether the SCP, indirect communication, ordelegated discovery is used) at operation 1003.

FIG. 11 is a diagram illustrating an NF registration process accordingto an embodiment of the disclosure.

Referring to FIG. 11 , one NF of the network (operating as a consumerNF) may transmit a request message for a specific service to another NF(operating as a producer NF) at operation 1101. Here, the requestmessage transmitted by the consumer NF may include parameters forperforming the corresponding service and information on the supportedfeatures of the consumer NF. The information on the supported featuresmay include indications of whether indirect communication, delegateddiscovery, SM context transfer, binding indication, and NF set aresupported particularly as enhancements to the SBA, among the functionssupported by the consumer NF. The supported features may be included asone of service request parameters, or may be separated and included inthe request message as separate data.

The producer NF may process the service request from the consumer NF andtransmit a response message corresponding thereto at operation 1102.Here, the response message transmitted by the producer NF may includeparameters for the result of performing the corresponding service andinformation on the supported features of the producer NF. Theinformation on the supported features may include indications of whetherindirect communication, delegated discovery, SM context transfer,binding indication, and NF set are supported particularly asenhancements to the SBA, among the functions supported by the producerNF. The supported features may be included as one of service resultparameters, or may be separated and included in the response message asseparate data.

The consumer NF and the producer NF may store the information exchangedtherebetween, and may perform subsequent operations by using thereceived information (information on peer NFs, whether the SCP, indirectcommunication, or delegated discovery is used) at operation 1103.

FIG. 12 is a diagram illustrating a method for an NF to receive SCPinformation through an NRF according to an embodiment of the disclosure.

Referring to FIG. 12 , one NF of the network (which can operate as aconsumer NF or a producer NF) may transmit a discovery request messageto the NRF to receive information for using the SCP in the configurationof the network at operation 1201. Here, the request message transmittedby the NF may include a parameter indicating that the target ofdiscovery is an SCP and information on supported features of the NF. Theinformation on the supported features may include indications of whetherindirect communication, delegated discovery, SM context transfer,binding indication, and NF set are supported, particularly asenhancements to the SBA, among the functions supported by the NF. Thesupported features may be included as one of service request parameters,or may be separated and included in the request message as separatedata. In addition, when the requesting NF needs to receive SCPinformation for a specific NW slice, it may include the identifier ofthe target slice in the request message. The above request may be aregular NF discovery request, a SCP discovery request for the SCP only,or a request for receiving message delivery/routing information.

The NRF may search for a SCP that satisfies the condition for therequest of the NF and transmit a response message at operation 1202. Theresponse message may include information about the SCP that therequesting NF can use (SCP address, NF ID, identifiers of slicessupported by the SCP, connection relationship between the SCP and otherSCPs, or the like) and supported features of the SCP. The response ofthe NRF may additionally include information to be applied when therequesting NF uses the SCP in the network to communicate with other NFs.This may include the operation mode of the SCP (one of modes A, B, C andD), whether indirect communication is used, and whether delegateddiscovery is used. If there is no SCP that satisfies the request of theNF, the NRF may explicitly notify this to the NF through the responsemessage. The above response is a response for the request message fromthe NF, that is, a response corresponding to a regular NF discoveryrequest, a SCP discovery request for the SCP only, or a request forreceiving message delivery/routing information. If the connectionbetween the NF and the SCP is composed of multiple hops in the networkconfiguration, the discovery response may include information about thenext-hop NF (or SCP) only from the viewpoint of the discovery requestingNF (or SCP), or may include information about all NFs (or SCPs) alongthe hop sequence on the transmission path.

The NF may store the information received from the NRF, and may performsubsequent operations by using the received information (whether the SCPis used, SCP address, NF ID, whether indirect communication or delegateddiscovery is used, or the like) at operation 1203. If the receivedresponse message contains information that there is no SCP or does notcontain SCP information, the NF may assume that there is no SCP forsubsequent operations.

FIG. 13 is a block diagram of a terminal according to an embodiment ofthe disclosure.

Referring to FIG. 13 , the terminal may include a transceiver 1310, aterminal controller 1320, and a storage 1330. In the disclosure, theterminal controller 1320 may be defined as a circuit, anapplication-specific integrated circuit, or at least one processor.

The transceiver 1310 may transmit and receive signals to and fromanother network entity. The transceiver may receive system information,a synchronization signal, or a reference signal from, for example, abase station.

The terminal controller 1320 may control the overall operation of theterminal according to an embodiment proposed in the disclosure. Forexample, the terminal controller may control signal flows between blocksto perform operations according to the above-described drawings andflowcharts. Specifically, the terminal controller may operate accordingto a control signal from the base station and may exchange messages orsignals with another terminal and/or network entity.

The storage 1330 may store at least one of information transmitted andreceived through the transceiver 1310 or information generated throughthe terminal controller.

FIG. 14 is a block diagram of a base station according to an embodimentof the disclosure.

Referring to FIG. 14 , the base station may include a transceiver 1410,a base station controller 1420, and a storage 1430. In the disclosure,the base station controller 1420 may be defined as a circuit, anapplication-specific integrated circuit, or at least one processor.

The transceiver 1410 may transmit and receive signals to and fromanother network entity. The transceiver may transmit system information,a synchronization signal, or a reference signal to, for example, aterminal, and may receive information from an NF to provide a service tothe terminal.

The base station controller 1420 may control the overall operation ofthe base station according to an embodiment proposed in the disclosure.For example, the base station controller may control signal flowsbetween individual blocks to perform operations according to theabove-described drawings and flowcharts. Specifically, the base stationcontroller may exchange messages or signals with a terminal, anotherbase station and/or network entity.

The storage 1430 may store at least one of information transmitted andreceived through the transceiver or information generated through thebase station controller.

FIG. 15 is a block diagram of an NF (including an NF instance) accordingto an embodiment of the disclosure.

The NF shown in FIG. 15 may include at least one of the AMF, master AMF,NSSF, SCP, or NRF described above, and is not limited to a specific NF.

Referring to FIG. 15 , the NF may include a transceiver 1510, an NFcontroller 1520, and a storage 1530.

The transceiver 1510 may transmit and receive signals to and fromanother network entity. The transceiver may transmit data and controlinformation for providing a service to a base station (RAN), and maytransmit information according to the disclosure to another NF.

The NF controller 1520 may control the overall operation of the NFaccording to an embodiment proposed in the disclosure.

The storage 1530 may store at least one of information transmitted andreceived through the transceiver or information generated through the NFcontroller.

The methods according to the embodiments described in the claims orspecification of the disclosure may be implemented in the form ofhardware, software, or a combination thereof.

When implemented in software, a computer-readable storage medium storingone or more programs (software modules) may be provided. The one or moreprograms stored in the computer-readable storage medium are configuredto be executable by one or more processors of an electronic device. Theone or more programs include instructions that cause the electronicdevice to execute the methods according to the embodiments described inthe claims or specification of the disclosure.

Such a program (software module, software) may be stored in a randomaccess memory, a nonvolatile memory, such as a flash memory, a read onlymemory (ROM), an electrically erasable programmable read only memory(EEPROM), a magnetic disc storage device, a compact disc ROM (CD-ROM), adigital versatile disc (DVD), other types of optical storage devices, ora magnetic cassette. Or, such a program may be stored in a memorycomposed of a combination of some or all of them. In addition, aplurality of component memories may be included.

In addition, such a program may be stored in an attachable storagedevice that can be accessed through a communication network, such as theInternet, an intranet, a local area network (LAN), a wide area network(WAN), or a storage area network (SAN), or a communication networkcomposed of a combination of these. Such a storage device may access thedevice that carries out an embodiment of the disclosure through anexternal port. In addition, a separate storage device on a communicationnetwork may access the device that carries out an embodiment of thedisclosure.

While the disclosure has been shown and described with reference tovarious embodiments thereof, it will be understood by those skilled inthe art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the disclosure as definedin the appended claims and their equivalents.

What is claimed is:
 1. A method performed by a service communication proxy (SCP) entity in a wireless communication system, the method comprising: transmitting, to a network repository function (NRF) entity, a first message comprising a parameter indicating a type of a target NF to be discovered is an SCP; and as a response to the first message, receiving, from the NRF entity, a second message comprising information associated with the target NF, wherein in case that the type of the target NF is the SCP, the information associated with the target NF comprises at least one of the type of the target NF indicating the SCP, an NF identifier of the target NF, or an address of the target NF.
 2. The method of claim 1, wherein the first message further comprises NF set information associated with an NF entity served by the target NF or a network slice related identifier associated with the target NF.
 3. The method of claim 1, wherein the information further comprises a network slice related identifier associated with the target NF.
 4. The method of claim 1, wherein the information further comprises SCP domain information associated with another SCP entity interconnected with the target NF.
 5. The method of claim 1, wherein the information further comprises at least one of NF set information associated with an NF entity served by the target NF, or endpoint addresses accessible via the target NF.
 6. A method performed by a network repository function (NRF) entity in a wireless communication system, the method comprising: receiving, from a service communication proxy (SCP) entity, a first message comprising a parameter indicating a type of a target NF to be discovered is an SCP; and as a response to the first message, transmitting, to the SCP entity, a second message comprising information associated with the target NF, wherein in case that the type of the target NF is the SCP, the information associated with the target NF comprises at least one of the type of the target NF indicating the SCP, an NF identifier of the target NF, or an address of the target NF.
 7. The method of claim 6, wherein the first message further comprises NF set information associated with an NF entity served by the target NF or a network slice related identifier associated with the target NF.
 8. The method of claim 6, wherein the information further comprises a network slice related identifier associated with the target NF.
 9. The method of claim 6, wherein the information further comprises SCP domain information associated with another SCP entity interconnected with the target NF.
 10. The method of claim 6, wherein the information further comprises at least one of NF set information associated with an NF entity served by the target NF, or endpoint addresses accessible via the target NF.
 11. A service communication proxy (SCP) entity in a wireless communication system, the SCP entity comprising: a transceiver; and at least one controller coupled with the transceiver and configured to: transmit, to a network repository function (NRF) entity, a first message comprising a parameter indicating a type of a target NF to be discovered is an SCP, and as a response to the first message, receive, from the NRF entity, a second message comprising information associated with the target NF, wherein in case that the type of the target NF is the SCP, the information associated with the target NF comprises at least one of the type of the target NF indicating the SCP, an NF identifier of the target NF, or an address of the target NF.
 12. The SCP entity of claim 11, wherein the first message further comprises NF set information associated with an NF entity served by the target NF or a network slice related identifier associated with the target NF.
 13. The SCP entity of claim 11, wherein the information further comprises a network slice related identifier associated with the target NF.
 14. The SCP entity of claim 11, wherein the information further comprises SCP domain information associated with another SCP entity interconnected with the target NF.
 15. The SCP entity of claim 11, wherein the information further comprises at least one of NF set information associated with an NF entity served by the target NF, or endpoint addresses accessible via the target NF.
 16. A network repository function (NRF) entity in a wireless communication system, the NRF entity comprising: a transceiver; and at least one controller coupled with the transceiver and configured to: receive, from a service communication proxy (SCP) entity, a first message comprising a parameter indicating a type of a target NF to be discovered is an SCP, and as a response to the first message, transmit, to the SCP entity, a second message comprising information associated with the target NF, wherein in case that the type of the target NF is the SCP, the information associated with the target NF comprises at least one of the type of the target NF indicating the SCP, an NF identifier of the target NF, or an address of the target NF.
 17. The NRF entity of claim 16, wherein the first message further comprises NF set information associated with an NF entity served by the target NF or a network slice related identifier associated with the target NF.
 18. The NRF entity of claim 16, wherein the information further comprises a network slice related identifier associated with the target NF.
 19. The NRF entity of claim 16, wherein the information further comprises SCP domain information associated with another SCP entity interconnected with the target NF.
 20. The NRF entity of claim 16, wherein the information further comprises at least one of NF set information associated with an NF entity served by the target NF, or endpoint addresses accessible via the target NF. 